Monitoring system and method for connecting a monitoring device to a service server

ABSTRACT

A method according to the invention for connecting a monitoring device to a service server may comprise retrieving an address relating to a control server from a memory of the monitoring device, sending a connection message from the monitoring device to the address relating to a control server in response to a connecting event, extracting, at the control server, an identifier from the communication between the monitoring device and the control server, identifying, at the control server, a service server associated with the extracted identifier, sending an address relating to the identified service server from the control server to the monitoring device, sending a connection message from the monitoring device to the identified service server in response to the receipt of the address related to the identified service server, establishing a service connection between the monitoring device and the identified server.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of prior filed co-pendingProvisional Application No. 60/776,976 filed on Feb. 25, 2006 entitled“Monitoring System and Method for Connecting a Monitoring Device to aService Server” (Atty. Docket # AWAPP0014P); and European PatentApplication No. EP05112794.2, filed Dec. 22, 2005 entitled “MonitoringSystem and Method for Connecting a Monitoring Device to a ServiceServer” which are incorporated herein by reference in their entirety asif fully set forth herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to monitoring systems and devices of sucha system. In particular the invention relates to a method for connectinga monitoring device to a service server and to a monitoring systemenabling such connection.

2. Description of the Related Art

Monitoring systems for monitoring of premises, areas of particularinterest and/or processes connected via a computer network to monitoringor surveillance servers are increasingly popular, in particular suchmonitoring systems including digital monitoring cameras. One reason forthe popularity of such systems may be that the systems in great extentmay utilize an existing network, if a computer network already is inplace.

Another reason for using a general computer network as a surveillancenetwork may be that the network that has to be built for the monitoringsystem may be used to connect other types of equipment, e.g. computers,servers and peripherals. For these reasons the technology suitsorganizations/persons in need of only a single or few monitoring devicesas well as organizations/persons in need of a great number of monitoringdevices.

In one such monitoring system the monitoring devices are arranged tosend their monitoring data to a service server which processes themonitoring data or information in order to prepare the data for accessto monitoring data by a user, for logging monitoring information, forstoring monitoring data, or for other purposes known to a person skilledin the art of monitoring systems.

In general the monitoring devices of such system are manufactured by onecompany and the service server is maintained by a monitoring serviceprovider, being another company. The monitoring service provider may bea company or organization specialized in providing such services. Themonitoring service provider may, however, also be a company related tothe monitored premises, areas and/or processes, i.e. the company owningor operating at the monitored sites. In the systems of today eachmonitoring device may be provided with the address to a service serverby the user keying the address directly into the monitoring device.Another method for achieving a connection between the monitoring deviceand a service server is to connect to the service server via a computerconnected to the computer network and register the monitoring device atthe service server.

Today, such programming of an address to a service provider orregistration of a monitoring device in a service server is performed bythe user of or a person installing the monitoring device during theprocess of installing the monitoring device.

Some general problems associated with the above described monitoringsystems are that the person performing the installation may not beexperienced in programming monitoring devices, the programming may betime consuming, the person may enter erroneous data into the monitoringdevice.

SUMMARY OF THE INVENTION

One object of the present invention is to provide an improved monitoringsystem.

The object is achieved by means of a method for connecting a monitoringdevice to a service server according to claim 1 and by means of amonitoring system according to claim 11, a control server according toclaim 18, and a monitoring device according to claim 21. Embodiments ofthe invention are disclosed in the dependent claims.

In particular, according to a first aspect of the invention a method forconnecting a monitoring device to a service server, comprises retrievingan address relating to a control server from a memory of the monitoringdevice, sending a connection message from the monitoring device to theaddress relating to a control server in response to a connecting event,extracting, at the control server, an identifier from the communicationbetween the monitoring device and the control server, identifying, atthe control server, a service server associated with the extractedidentifier, sending an address relating to the identified service serverfrom the control server to the monitoring device, sending a connectionmessage from the monitoring device to the identified service server inresponse to the receipt of the address related to the identified serviceserver, establishing a service connection between the monitoring deviceand the identified server.

According to a second aspect of the invention the monitoring systemcomprises a monitoring device, a control server, a plurality of serviceservers and a network connecting the servers and the monitoring device.

The monitoring device includes a memory including a connection addressinitiating means arranged to send a connection message over the networkto the connection address in response to an initiation event, and meansarranged to send a new connection message to an address received in amessage via said network.

The control server includes an identity extractor arranged to extract anidentifier from a communication between the monitoring device and thecontrol server, matching means arranged to match the extractedidentifier to a control server or a service server and retrieve anaddress to the matched service server, and a message generator arrangedto generate a message including the retrieved address and to send thegenerated message to the monitoring device.

Each service server includes means for receiving and processingmonitoring data from a monitoring device.

An advantage with the above described method and system is that themaintenance and installation of the device may be facilitated because ofthe monitoring device being guided to a preferred service server by acontrol server instead of requiring a person to key in the address to apreferred service server. Additionally, in this way the system may bemore efficiently maintained, because the control server may be easier ormore effective to keep updated with new or changing service serveraddresses than the user or the person maintaining the monitoring device.

A further advantage is that the monitoring device initiates allconnections with the control server/servers and the serviceserver/servers, which facilitate the integration of monitoring devicesfrom behind access limiting devices, e.g. a firewall, a NAT (NetworkAddress Translation), an ISP (Internet Service Provider) providingdynamic addresses, into a system reaching outside such access limitingdevices.

According to another embodiment of the invention an initial retrieval ofan address relating to a control server from a memory of the monitoringdevice in the above mentioned method returns a preconfigured addressrelating to a control server and wherein an initial sending of aconnection message from the monitoring device to the preconfiguredaddress is performed in response to an initiation event of themonitoring device.

The advantage of arranging an initial control server like this is thatthe installation and customization of monitoring devices of the systemis facilitated. The installation is facilitated as a result of theinitiation of the monitoring device automatically contacts apredetermined control server upon initiation of the monitoring device,thus no need to provide any addresses to the monitoring device duringinstallation. The customization is facilitated because specificproperties relating to the monitoring device may be provided by thecontrol server upon initial communication between the monitoring deviceand the control server, i.e. the initial control server. Accordingly,the manufacturer of the monitoring device does not need to havedifferent manufacturing processes for different batches of monitoringdevices.

In other words the system according to this embodiment of the inventionmay solve problems of the manufacturer relating to customization ofdevices. For example, during manufacturing the monitoring devices of themonitoring systems of today have to be associated with different serviceproviders and then each device associated with a service provider has tobe programmed in a process that is customized for the associated serviceprovider. Thus, the manufacturer has to provide a plurality of differentmanufacturing processes for devices intended for different serviceproviders. More over the devices so programmed for a specific serviceprovider have to be delivered and sold to the specific service provideror customers of the specific service provider.

Another advantage of this embodiment is that it enables centralmanagement of monitoring devices.

According to yet another embodiment the sending of a connection messagefrom the monitoring device to a control server is performed at least onetime prior to sending a connection message from the monitoring device toa control server which provides an address of a service server to themonitoring device.

The advantage of arranging a plurality of control servers and directinga monitoring device to another control server is that the responsibilityof directing the monitoring device to a correct service server may bechanged from an entity responsible of the general functionality of thesystem, e.g. the manufacturer of the monitoring device, to an entityresponsible for providing the required service, e.g. the serviceprovider.

According to a further embodiment the act of identifying a serviceserver further includes the acts of extracting a network addressrelating to the monitoring device from the communication between themonitoring device and the control server, matching the network addressto a service provider, and selecting a service server associated withthe matched service provider.

By using the network address relating to the monitoring device in thisway it may be easy to identify the service provider, at least in thosecases the service provider providing the network connection isassociated to a provider of a monitoring service or if those serviceproviders are the same.

According to yet another embodiment the act of identifying a serviceserver further includes the acts of extracting an identification codeincluded by the monitoring device in the communication between themonitoring device and the control server, matching said identificationcode to a service provider, and selecting a service server associatedwith the matched service provider.

By using an identification code in this way the monitoring devices maybe customized and connected to a specific monitoring service providerbased on various criteria. For instance a batch of monitoring devicesmay be dedicated to a specific monitoring service provider offering adiscount when buying the monitoring device with the reservation that thedevice will be connected to service servers of that monitoring serviceprovider. Thus, the service provider get the identification codesregistered in the control server as identification codes belonging tothe service provider and is thereby able to ensure the connection of themonitoring device to the services of the service provider. Further, thebatch of monitoring devices may be dedicated to a company having aservice server of their own for the monitoring of their own premises.

In all the embodiments it is the monitoring device which sends theconnection message to the control server or to the service server. Theadvantage of this is that the servers may be arranged to send controlmessages in the responses to the messages from the monitoring device,e.g. in the response to a http request. Thus the control server mayexercise control over the monitoring device despite possible accesshindering devices, e.g. firewalls, NAT servers, etc., arranged betweenthe monitoring device and the server. Such a communication scheme isdisclosed in WO 2006/073348, by Axis AB, Emdalavägen 14, S223 69 Lund,SE.

According to one embodiment the system includes a plurality of controlservers including at least one initial control server, being a highlevel, or even a top level, control server in an hierarchy of controlservers. Such initial control server is arranged to access addressinformation enabling at least indirect connection to any control serverand service server in the system.

By arranging the system like this it is possible to distributeresponsibilities among the servers. For instance, the initial controlserver may be given an overall responsibility of directing a monitoringdevice to the correct subsystem of control servers and service servers,while a control server in such a subsystem may be given theresponsibility to direct the monitoring device to the most suitableservice server.

A further scope of applicability of the present invention will becomeapparent from the detailed description given below. However, it shouldbe understood that the detailed description and specific examples, whileindicating preferred embodiments of the invention, are given by way ofillustration only, since various changes and modifications within thespirit and scope of the invention will become apparent to those skilledin the art from this detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features and advantages of the present invention will becomeapparent from the following detailed description of a presentlypreferred embodiment, with reference to the accompanying drawings, inwhich

FIG. 1 is a schematic overview of a monitoring system according to thepresent invention,

FIG. 2 is a schematic timing diagram over signaling in one embodiment ofthe invention,

FIG. 3 a is a schematic block diagram of a monitoring device accordingto one embodiment of the invention,

FIG. 3 b is a schematic block diagram of a video camera acting asmonitoring device according to one embodiment of the invention,

FIG. 4 a is a schematic flowchart of the process of a monitoring deviceaccording to one embodiment of the invention,

FIG. 4 b is a schematic flowchart of the process of a monitoring deviceaccording to another embodiment of the invention,

FIG. 5 is a schematic block diagram of a control server according to oneaspect of the invention,

FIG. 6 a is a schematic flowchart of the process of a control serveraccording to one embodiment of the invention,

FIG. 6 b is a schematic flowchart of the process of a control serveraccording to another embodiment of the invention,

FIG. 7 is a schematic block diagram of a service server according to oneembodiment of the invention,

FIG. 8 is a schematic flowchart of the process of a service serveraccording to one embodiment of the invention,

FIG. 9 is a schematic diagram over one configuration of a monitoringsystem according to the present invention,

FIG. 10 is a schematic diagram over another configuration of amonitoring system according to the present invention,

FIG. 11 is a schematic diagram over yet another configuration of amonitoring system according to the present invention,

FIG. 12 is a schematic flowchart of a scenario for connecting amonitoring device to a service server and providing a user access to themonitoring device,

FIG. 13 is a schematic flowchart of another scenario for connecting amonitoring device to a service server and providing a user access to themonitoring device, and

FIG. 14 is a schematic diagram over possible handover relations in apossible configuration of a monitoring system according to theinvention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In FIG. 1 an overview of a monitoring system 10 according to oneembodiment of the invention is showed. The monitoring system 10 includesa monitoring device 20, a control server 30, a service server 40 and auser terminal in the form of a client computer 42 or a mobile telephone44. The monitoring device 20, the control server 30, and the serviceserver 40 are connected to each other via a computer network 50, such asInternet, a LAN (Local Area Network), a WAN, (Wide Area Network). Thecomputer network 50 may include wireless and/or wired communicationchannels. The monitoring device 20 may be a digital camera, a motiondetector, an audio detector, an IR-detector, a passage control device,an electronic door lock, an elevator control system, a card reader, etc.The user terminals 42,44 are connected to the network communicating withthe service server for accessing a monitoring device or accessingmonitoring service implemented on the service server.

In FIG. 2 a general signaling scheme between the different devices areschematically depicted. The specifics of the communication betweendevices may vary depending on the communication protocols used and thephysical network. However, details regarding how to implement generalcommunications via a network are known to persons skilled in the art ofcomputer communications and are therefore not described herein. Themonitoring device 20 is arranged to send a connection message 600 inresponse to an initiation action or an initiation event to an addressstored within the monitoring device 20. The connection message isreceived at a control server 30 residing at said address. The controlserver 30 receives the connection message and the monitoring device 20and the control server 30 establish a connection. The control serveralso extracts an identifier from the communication received from themonitoring device 20. The identifier is used to match the monitoringdevice to a service provider and a service server. When the controlserver 30 has found a match it sends an address in a message 602 to themonitoring device. The message is identified as a change of addressmessage or a reconfiguration message at the monitoring device 20. Inresponse to this message 602 the monitoring device 20 stores the newaddress and sends a connection message 600 or 604 to the new address.The address received from the control server 30 may address anothercontrol server 30 or a service server 40 depending on the structure ofthe system, this will be explained below.

When the address in the reconfiguration message 602 received at themonitoring device is associated with a service server 40 and,accordingly, the next connection message 604 sent from the monitoringdevice 20 is sent to a service server 40, the service server 40 and themonitoring device 20 then establish a service connection 606 enablingcommunication of monitoring data to the service server 40 and possibly,but not necessary, configuration parameters to the monitoring device.Thus, the monitoring device 20 has been connected to a server that isenable to provide the monitoring services. The service server 40 towhich the monitoring device 20 has been directed may then be the mostsuitable service server 40 in regard of geographic location, location inthe network, available services, and/or customer specific reasons. Whichone of these criteria that is applicable in regard of specificmonitoring devices 20 may be controlled by the data provided to thecontrol server 30 or control servers 30 directing the monitoring device20 to the service server 40.

According to one embodiment the monitoring device 20 may include aninput means 202, a processing means 204, a non volatile memory 206, avolatile memory 208, a network interface 210, an initiating means 212, amonitoring device means 216 as shown in FIG. 3 a and in FIG. 3 b. FIG. 3a is a schematic view of a general monitoring device and FIG. 3 b is aschematic view of a monitoring device 20 being a digital camera. Inorder to facilitate the understanding of the invention the FIGS. 3 a and3 b do not show all means needed to make the device perform its normalfunctions, i.e. the means that makes an IR detector function as an IRdetector or that makes a digital camera function as a digital camera.All means, such as hardware and software, required to make themonitoring device work as a monitoring device is indicated by themonitoring device means 216 in FIG. 3 a. In FIG. 3 b the correspondingmeans of the camera is referred to as video camera means 218. The meansand arrangements required for making an ordinary monitoring devicenetwork enabled are known to a skilled person. An example of suchnetwork enabled monitoring devices on the market today are the networkeddigital cameras from Axis Communications AB, Emdalavägen 14, S-223 69Lund, Sweden.

As described above the monitoring device 20 may be any type of aplurality of types of devices and the input means 202 of the monitoringdevice 20 is different in different types of monitoring devices. Forinstance, the input means 202 of the digital camera 20 a in FIG. 3 b maybe an image sensor, e.g. a CCD, the input means of an audio detector maybe a microphone, etc. The main function of the input means 202 is todetect, sample or measure the properties monitored by the monitoringdevice 20 and provide such data to the processing means 204 for furtherprocessing.

The processing means 204 is arranged to control the functionality of themonitoring device and execute program code related to the functions ofthe present invention and general functions of the monitoring device 20.The non volatile memory 206 may be used by the monitoring device 20 forstoring data and information relating to the functionality of themonitoring device and its interaction with the monitoring system. Inparticular, according to one embodiment of the invention, a list 214 ofaddresses to servers on the network is stored in the non volatilememory. The list 214 of addresses may be prioritized by marking eachaddress entry with a priority marker. The markers may be numbersidentifying the priority. The list 214 of addresses in a monitoringdevice shipped from the manufacturer includes at least one preprogrammedaddress to a control server 30, this server is generally referred to asinitial control server in this application. The list 214 may include aplurality of addresses wherein the address marked as having the highestpriority is the first address the monitoring device will send aconnection message to in response to a connection event. In case thatthe first address fails the next address in the prioritized list istried and a connection message is sent to that one as well. According toanother embodiment the next address tried in the list 214, in case ofthe first address failing, is randomly selected, which may result inload distribution in the network in case of many devices being equippedwith identical lists and trying to connect to a faulty addressessentially simultaneously.

The non volatile memory may also comprise an identity code uniquelyidentifying the monitoring device and a unique key for encryption. Theidentity code may be used to identify the monitoring device at a controlserver or a service server. The unique key may be used forauthenticating the camera as being the camera stated by the identitycode.

The volatile memory 208 may be used to support the processing means 204and/or to temporarily store addresses received from control servers.Accordingly, the volatile memory 208 may also be a memory used by theapplications executed on the monitoring device 20 by the processingmeans 204.

The network interface 210 is the interface between the monitoring device20 and the network 50. Hardware and software that may be used toimplement the network interface 210 for a number of different networksare well known by the person skilled in the art of computer networks.

The initiation means 212 is a means generating an initiation event andthereby triggering the sending of the initial connection message to theprioritized address stored in the non volatile memory 206. According toone embodiment the initiation means 212 is a detector enabled to detectthe connection of the monitoring device 20 to a network 50, i.e. eitherthe connecting of a powered monitoring device 20 to a network 50 or thepowering up of a monitoring device 20 already physically connected to anetwork 20. By arranging such an initiation means 212 the searching andconnecting to a suitable service server 40 may be fully automated.According to another embodiment the initiation means 212 may be a poweron button of the monitoring device 20 or it may be a button dedicatedfor the initiation of the connecting of the monitoring device 20 to aservice server 40.

Means 218 arranged to send a connection message to a control server 30or a service server 40 in response to a message including an address tosuch a server or a reconfiguration message including an address to sucha server may be implemented by program code executed by the processingmeans 204.

Returning to the unique key stored in the non volatile memory 206, itmay also be used for encrypting messages to be sent or for decryptingreceived messages.

Further the key may be utilized to authenticate the camera during thesetup of a connection resulting in an open path as described in WO2006/073348, by Axis AB, Emdalavägen 14, S223 69 Lund, SE. The controlserver and the service server may also be provided with a key in orderto be able to decrypt messages from the monitoring device, to encryptmessages sent to the monitoring device and to authenticate themonitoring device. Thereby all communication between the monitoringdevice and the control server and/or the service server may beencrypted. Preferably there is provided a unique key for each monitoringdevice produced and the key may be stored in the monitoring deviceduring manufacturing of the device. The keys may be keys of a sharedsecret system or a public key system.

According to one embodiment a very large list of different keys aregenerated before the manufacturing of the cameras which are to beprovided with these keys. The list should be of such a size that no newlist has to be generated for years. Each control server is provided withthe list of keys and during the manufacturing of a monitoring device thedevice will be provided with one of the keys. By providing the keys inthis way there is no need for distribution of keys, which may be asafety hazard. Accordingly, authentication of monitoring devices and thedistribution of keys may be simplified.

The process of the monitoring device 20 finding a service server 40,according to one embodiment, is illustrated in FIG. 4 a. Initially themonitoring device 20, which is either offline or shut off, is initiated,i.e. connected to the network, powered up, or initiated in any other waydescribed above, step 620.

The monitoring device 20 then retrieves the first address from theprioritized list in the non volatile memory 206, step 622. This addressmay be the address stored by the manufacturer during the manufacturingprocess. However, if the monitoring device 20 has been previouslyconnected to a system according to the invention the address may be anaddress stored in response to a reconfiguration message or anothermessage including an address to a more suitable server than the serverof the address provided in the monitoring device 20 during manufacturingof the device.

Then the monitoring device sends a connection message via the networkinterface 210 to a server associated with the retrieved address, step624.

After the connection message has been sent the monitoring device waitsfor a response from the server that received the connection message.

If, in step 626, the response is a message including an address to a newserver or if the response is a reconfiguration message including anaddress to a new server, the monitoring device stores this address inthe non volatile memory 206, step 628. The address may be stored as themost prioritized in the list 214. The response message orreconfiguration message from the server may, according to one specificembodiment, include an entirely new list of server addresses replacingthe present list in the non volatile memory 206 or a subset of addressessubstituting some of the addresses in the present list.

Then the monitoring device sends a new connection message, step 630, tothe new server address, or the first address in the prioritized listafter the list has been changed in step 628, in response to the receivedmessage. Then the monitoring device 20 once more waits for a responsefrom the server to which the connection message was sent.

If, in step 626, no new server address is identified in the responsemessage the monitoring device 20 check if the response includes anindication of the server being a service server 40 in itself, step 632.If the response includes such an indication the monitoring device 20 andthe service server establish a service connection, step 634.

If the response does not include an indication of the server being aservice server then the monitoring device may wait for another messagefrom the server. In another embodiment the monitoring device sends aconnection message to another address in the list directly when aresponse message is determined not to identify the server as a serviceserver or not to identify a new server address. In another embodimentsuch a connection message is sent to another address in the list after acounter or timer indicate that the server or the address is likely to beerroneous. Said another address may be the next address in a prioritizedlist or a random selection in the list, as described earlier.

In another embodiment, illustrated in FIG. 4 b, the step 622 ofretrieving a server address from the non volatile memory monitoringdevice additionally includes retrieving an identity code and anauthentication code. The identity code being an identifier uniquelyidentifying the monitoring device, e.g. such as a serial number, aproduct code combined with an item specific code, etc. Theauthentication code may be a code encrypted by means of the key storedin the volatile memory 206. The identifier and the authentication codeis then sent, step 625, to the server 30 of the retrieved address eitherin the connection message, step 624, or in a later communication withthe server 30. Moreover, the response from the control server includingthe new server address may also include a second authentication code,which may be used for authentication of the monitoring device whenconnecting to a service server. The authentication code may be aencryption/decryption key generated by the control server. The purposeof this second authentication code is to avoid distributing the mainauthentication code or key because such distribution might tamper thesecrecy of the code.

In FIG. 5 one embodiment of the control server 30 is schematicallyillustrated. The automatic connection set up by the monitoring device 20is analyzed in the control server and the control server 30 provide themonitoring device 20 with an address to a new server, being the mostrelevant based on the information of other servers available to thecontrol server 30 and the information provided in the communication withthe monitoring device 20. The control server 30 includes a networkinterface 310 in order to provide network communications, a processingmeans 312 for operation of the control server 30, a memory 314 forsupporting and storing application programs executed by the processingmeans 312, an identity extractor 316 for extracting an identifier of amonitoring device from the communication between the monitoring device20 and the control server 30, an authenticator 317 for authenticatingthe identity code of the monitoring device 20, matching means 318 formatching the identity code to a server and a reconfiguration messagegenerator 320 for generating and sending an address associated to aserver matched to the extracted identifier.

The identity extractor 316 may be arranged to extract an identifier fromthe communication between the control server 30 and a monitoring deviceby extracting the address of the monitoring device connecting to thecontrol server 30, the address may for instance be the IP-address of themonitoring device 20. The IP-address may be used for identifying theoperator of the network in which the monitoring device is connected.This is possible because each operator has assigned series ofIP-addresses. The extraction is performed by an IP-address 322 extractorwhich may be arranged to pinpoint the response address included in themessage originating from the monitoring device 20. According to anotherembodiment the identity extractor 316 includes an identity codeextractor 324 arranged to extract an identity code and an authenticationcode sent by the monitoring device 20 in the communication between thecontrol server 30 and the monitoring device 20. In one embodiment thecontrol server 30 includes both the IP-address extractor 322 and theidentity code extractor 324 and may use them in accordance withdifferent schemes, e.g. the identity extractor may start to extract andtest if the IP-address is associated to a server in a database 330 andif not continue with a identity code check or the identity extractor maybe arranged to start to extract and test the identity code and then theIP-address.

The matching means 318 makes use of the identifier extracted by theidentity extractor 316 to find the most suitable server for themonitoring device. The matching means 318 is arranged to match theidentifier of the monitoring device to a server by accessing a list ordatabase 330 of identifiers and associated servers. The access of thelist or database is performed by means of a data base access means 326.The list or database 330 used for matching may be arranged in theserver, as a peripheral to the server, or it may be arranged for accessvia the network, the later embodiment is depicted in FIG. 5. The list ordatabase 330 may, according to one embodiment, include entries ofidentifiers and each identifier being associated with at least onecontrol server or service server. The list or database 330 may alsoinclude a key associated with each identifier for authenticating themonitoring device 20. Additional arrangements of the list or database330 is known to the skilled person.

The database 330 or list including the entries of identifiers, keys andinformation associating an identifier and a key of a monitoring device20 to a control server or a service server may be edited by accessingthe list or database 330. The database 330 or the list may requireauthorization in order to allow someone to edit. Such editing of thelist or database 330 may be performed in many different ways. Forexample, the editing may be performed in connection with the productionof the monitoring device, in such case the identity code of themonitoring device is entered and associated with a predetermined serviceprovider or server of a service provider, the editing may be performedby the service provider entering an identity code of a monitoring devicethat are to be associated to one or a set of their servers, the editingmay be performed by the service provider entering IP addresses of theirnetwork and associates these to one of or a set of their servers, etc.

One embodiment of the process of the control server 30 serving themonitoring device is showed in FIG. 6 a. The control server 30 receivesa connection message from a monitoring device 20, step 710, via thenetwork and the network interface 310. The monitoring device 20 and thecontrol server 30 establishes a connection for communication, step 712.Then the identity extractor 316 of the control server 30 extracts theidentifier and the authentication code associated with the monitoringdevice from the communication, step 714. The authenticity of theidentifier is then checked by means of the authentication code, step715. If the authentication fails, the process is ended, step 717.Otherwise the identifier is processed by the matching means 318, whichmatches the identifier to, in this particular embodiment, a serviceprovider, step 716.

If, step 718, no service provider is matched to the identifier then thecontrol server 30 may generate an error message, step 720, and returnthis message to the monitoring device 20 in a response to the connectionmessage. The monitoring device 20 may be arranged to display a specificerror code or activate some LED, Light Emitting Diode, indicating thetype of error.

If such an error occurs, the user may inform the support of themonitoring device or the service provider, depending on which of theparties who is to provide support, and they may enter a correct addressassociated to the monitoring device 20 or the IP address of themonitoring device 20, enter the identifier of the monitoring device inthe database and associate it to a server, etc.

If, step 718, a service provider is matched to the identifier then thematching means 318 retrieves an address to a server of that serviceprovider, step 722.

The retrieved server address is then passed to the reconfigurationmessage generator 320, which generates a reconfiguration message oranother type of message, step 724, including the retrieved serveraddress. Then the reconfiguring message is sent, step 726, to themonitoring device 20 and the monitoring device acts on the reconfiguringmessage as described above in connection with FIGS. 3-4. The controlserver 30 may also generate a second authentication code for sending tothe monitoring device 20, this authentication code may be sent to themonitoring device 20 in step 726 in connection with the reconfigurationmessage. The second authentication code may be used for authenticationof the monitoring device when connecting to a service server. Theauthentication code may be a encryption/decryption key generated by thecontrol server. The purpose of this second authentication code is toavoid distributing the main authentication code or key because suchdistribution might tamper the secrecy of the code.

The process described in FIG. 6 a may advantageously be implemented inan initial control server, i.e. the type of control server addressed bythe addresses arranged in the monitoring device during manufacturing ofthe monitoring device. Such a control server may be controlled by themanufacturer of the monitoring device and may present the benefit ofmaking it possible for the manufacturer to configure large series ofmonitoring devices using identical processes, programs and properties,independent of who will buy the device or which service provider thatare to be related to the monitoring device. The programs and propertiesof monitoring devices may be automatically changed when connecting tothe control server 30 for the first time in order to customize inaccordance with specific requests from service providers or otherparties related to the device. Such automatic changes are delivered tothe monitoring device 20 in a reconfiguration message.

Another embodiment of the process of a control server may be as showedin FIG. 6 b, the process is similar to the process of the embodiment inFIG. 6 a and therefore the same reference numerals are used for thesteps that are identical with the process of FIG. 6 a. The steps thatdiffers also uses the same reference numerals, but are marked with a thesymbol ′ after the number. Accordingly, the differences are generallythat the process of FIG. 6 b does not match a server by first matching aservice provider, but the server is directly matched to the identifier.Accordingly, the extracted identifier is matched to a server in the database, step 718′, and if a server is found, step 718′, the server addressassociated with the matched server is retrieved, step 722′. The rest ofthe process is identical to the process in FIG. 6 a.

A control server 30 like the one described in connection with FIGS. 5, 6a and 6 b may be used as an initial control server 30. Moreover, such acontrol server 30 may be useful as a later stage control server 30, i.e.a control server 30 arranged in a subsystem or a control server 30 of aservice provider that the initial control server 30 may provide theaddress to if not all the service server addresses of a service providerare stored in the database 330 utilized by the initial control server30. In this way different parties may manage different sets of serversin accordance with their objectives. For example, if the manufacturer ofthe monitoring devices manages a set of initial control servers and theservice providers manages service servers and possibly some controlservers, the manufacturer only is required to keep track of the serviceproviders and a subset of the servers of the service providers, whilethe service providers are allowed to set up their service servers asthey wish without having to consider changes to the database and controlserver of the manufacturer.

The service server 40 in the system may be seen as a server providing auser interface between the monitoring device 20 and user terminals. Theservice server 40 is arranged to provide a service connection to themonitoring device for transfer of the monitoring data to the serviceserver. Additionally, the service server may be arranged to process thedata received from the monitoring device 20 in order to present it ormake it possible for a client of a user to present. The service server40 may also be arranged to control the monitoring device. The serviceserver may, for example, be a server including communication means forcommunicating with a monitoring device and for communicating with a userterminal, such as a client computer, mobile telephone, etc. Further, theservice server may include authorization means in order to only connectauthorized users to the monitoring device. The authorization may beimplemented as a standard user name and password login. The user nameand password may initially be provided together with the monitoringdevice upon delivery. Moreover the service server may include a databasestoring the monitoring information from the monitoring devices. Suchmonitoring devices may be video sequences from a camera, events relatingto triggering of alarms, e.g. from an IR-detector or a sensor in a door.The service server may also be arranged to pass on substantially livevideo streams from cameras to user terminals upon request andauthorization from the user terminal.

In order to accomplish sending of control parameters, data, updates,etc., even to monitoring devices arranged behind access limitingdevices, e.g. a firewall, a NAT (Network Address Translation), an ISP(Internet Service Provider) providing dynamic addresses, the serviceserver 40 may be arranged to send such information in responses torequests sent from the monitoring device. This, is easily accomplishedas the monitoring device 20 is arranged to initiate the communications.

In one embodiment the service server, see FIG. 7, includes a networkinterface 410 for enabling communication with monitoring devices overthe network 50, processing means 412 for execution of applications onthe service server, a memory 414 to store applications data, and amonitoring data presentation means 416. The service server may alsoinclude an identity extractor 418 for extracting an identifier of amonitoring device from the communication between the monitoring device20 and the service server 40, an authenticator 324 for authenticatingthe identity code of the monitoring device 20, the authentication codeused for authentication in the service server may be said secondauthentication code. The identity extractor may further include anIP-address extractor 420 and/or a identity code extractor 422 having thesame functionality as in the control server 30. The monitoring datapresentation means 416 comprises one or a plurality of applications forenabling presentation of monitoring data from one or a plurality ofmonitoring devices. Service servers providing the possibility to receivemonitoring data, process the data and present the data for users areknown to persons skilled in the art. An example of an possible serviceserver 40 is found in WO 2006/073348, by Axis AB, Emdalavägen 14, S22369 Lund, SE. This application also describes a method for communicatingthrough access limiting devices.

One embodiment of the process relating to the invention of the serviceserver is shown in FIG. 8. The service server 40 receives a connectionmessage from a monitoring device 20, step 810, and identifies andauthenticates the monitoring device, step 811. Then the service serverand the monitoring device establishes a service connection, step 812.When the service connection is established the service server 40 maystart receiving monitoring data from the monitoring device, step 814,and processing, step 816, the received monitoring data in accordancewith the requirements of the service server 40 or the desires of thefinal user. Then the service server 40 may store the monitoring data,step 818, for presentation for a client of a user or for download to aclient or a server of the user. A client may be a workstation computer,a desktop computer, a laptop computer, a handheld computer, e.g. a PDA(Personal digital Assistant), a mobile telephone, etc.

The system for connecting a monitoring device to a service server mayinclude a plurality of monitoring devices 20, a plurality of controlservers and a plurality of service servers. The monitoring devices maybe connected to the network 50 directly, via another network, via anaccess limiting device, etc.

In FIG. 9 one example of a system including three monitoring devices20-22 and two service servers 40-41 and user terminals 42 and 44. Inthis example two of the monitoring devices are depicted as monitoringcameras, by using two visually differently looking figures of camerasand one general box indicating a monitoring device we want to emphasizethat the monitoring devices in the system are not necessarily identicalin regard of brand, type or even monitoring function, i.e. themonitoring system may include an IR detector, a wide angle camera, a lowresolution camera, simultaneously. The numbers of monitoring devices20-22 in the example illustrated by FIG. 9 may easily be increased aswell as the number of service servers 40-41. Additionally, the examplesystem includes one control server 30, which may be a manufacturercontrolled control server.

Further, one of the monitoring devices 22 is connected to the networkvia a access limiting device 60, e.g. a firewall, a NAT (Network AddressTranslation) server, an ISP (Internet Service Provider) providingdynamic addresses, firewall. Such an access limiting device are notlimiting the access of the monitoring device from the servers becausethey are arranged to send information or instructions to monitoringdevices in a way passing through such devices, e.g. by means ofproviding the information or instructions in responses to messages orrequests from the monitoring device. In the example, the databaseaccessed by the control server 30 during the process of matching each ofthe monitoring devices to a server may include information associatingthe IP-address of the monitoring device 20 to the service server 40,based on the fact that the IP-address of monitoring device 20 is anIP-address of an internet access provider providing the service server40. Additionally or alternatively, the database may include informationassociating an identity code sent from each of the monitoring devices 21and 22 with the service server 41. Accordingly, the control server 30may send the address of service server 40 to monitoring device 20 andthe address of service server 41 to monitoring devices 21 and 22 inresponse to the connection messages sent by each of the monitoringdevices, if the database of the control server include informationassociating the monitoring devices 20-22 to those service servers. Asdiscussed earlier, the addresses received at the monitoring devices maybe stored in non volatile memory in order to be used during a futureinitiation. For example if monitoring device 20 is disconnected andreconnected again the address of service server 40 may be stored in nonvolatile memory and the monitoring device may send the connectionmessage directly to service server 40 instead of sending it to thecontrol server 30. The user terminals 42 and 44 are arranged tocommunicate with the service server via the network in order to getmonitoring information or image sequences from the camera or to controlthe monitoring device. In cases where the monitoring device is connectedto the network via a access limiting device, such as a fire wall, themonitoring device has to be accessed via a server such as the serviceserver 40.

In FIG. 10, yet another possible configuration is presented. In thiscase we may assume that a company requiring a lot of monitoring devices20 for monitoring their premises, all connected to a protected 60private network 51, also connect a service server directly to theprivate network 51. User terminal 42 and 44 are connected to the serviceserver for accessing the monitoring services provided and/or foraccessing the monitoring devices of the user. When buying the monitoringdevices 20 they may get the serial numbers of the cameras registered inthe control server and associated to the address of the internal serviceserver of the company, the control server may be an initial controlserver. In this way the installation of the cameras are greatlysimplified because the monitoring devices 20 only have to be mounted andconnected to the private network 51 then the monitoring devices 20automatically finds and reconfigures to connect to the intended serviceserver 40 by means of the control server 30.

In FIG. 11 yet another configuration of the system is presented. Let usassume that a monitoring service provider also is a provider of servicessuch as network access, i.e. internet access. An IP-address, a portionof an IP-address, or a plurality of EP-addresses are stored in thedatabase related to the control server 30 of the manufacturer, i.e. asmuch info of the IP-address or as many IP-addresses that is needed foridentifying a monitoring device as being connected to a IP-address ofthe service provider is loaded into the database of the control server30. The service provider is also associated with the control server 31,which is a control server operated by the service provider. The serviceprovider have, for some reason, installed two service servers 40 and 41.

The control server 31 of the service provider is provided with adatabase, which is maintained by the service provider, includinginformation relating to which one of the service servers 4041 eachmonitoring device 22-25 should be connected to. The informationassociating a monitoring device 22-25 to a service server 4041 in thecontrol server 31 may, as above, be based on IP-addresses or it may bebased on unique codes identifying the specific monitoring device. Thus,when a monitoring device 24 is connected to the network of the serviceprovider 52 it sends a connection message to the control server 30, viathe network of the service provider 52 and another network 50. Thenetwork 50 may be Internet, a LAN, a WAN, or any other network, to whichthe control server is connected.

The control server 30 may, for example, then match the IP-address to theservice provider and the control server 31 and sends the addressassociated to the control server 31 to the monitoring device 24. Then,the monitoring device 24 sends a connection message to the controlserver 31. The control server 31 may then match the IP-address oranother identifier to the service server 41 and sends the addressassociated to the service server 41 to the monitoring device 24. Thenthe monitoring device 24 sends a connection message to the serviceserver 41 and a service connection may be established with serviceserver 41.

The monitoring devices 25 and 22 may be associated in the same way tothe service provider and the control server 31 of the service provider.However, the control server 31 may associate each of the monitoringdevices 25 and 22 to any one of service servers 40 and 41 depending onthe entries in the data base of control server 31. The reasons forassociating a monitoring device to a specific service server may vary.One reason may be that a service provider provides some service serversfor small and medium enterprises, some service servers for a moreinexpensive “home solution”, and some service servers for largeenterprises, possibly implementing customized applications.

The two monitoring devices 20 and 21 are not connected to the commonnetwork, e.g. Internet, via the network of the service provider. Thesemonitoring devices may anyway be associated to the service provider inthe figure. For instance may the control server 30 identify the serviceprovider to use by means of an identifier sent to the control server 30during communication between the control server 30 and each of themonitoring device.

FIG. 11 also discloses a login server 62 connected to the network 51 ofthe service provider. The login server 62 is arranged to be used in anembodiment where the user provides an identity code and a userauthentication code to the service provider who passes on the identitycode and the user authentication code to a control server 30 togetherwith an instruction to associate the monitoring device identified by theidentity code to said service provider. The purpose of theauthentication code is to prohibit unauthorized association of andaccess to a monitoring device. The login server 62 may be a stand alonedevice. However it may also be implemented in a service server 40, 41 ora control server 31 of the service provider.

In FIG. 12 an example of a scenario for connecting a monitoring deviceto a service server and providing access for a user to the monitoringdevice is described. In the scenario a monitoring device is manufacturedand in the manufacturing process a unique identity code and a unique keyis stored in the monitoring device, step 810. The identity code and theunique key have been described earlier in the application. Themanufacturer also stores the identity code and the unique key in a database of a control server, step 812. The identity code and the unique keyis then associated in the data base of the control server to an operatorof an internet access or a company providing surveillance solutions,step 814. The association of the monitoring device to any of thesecompanies may be a result of the company buying the monitoring device ora result of an agreement. Then the user buys the camera, maybe as partof a surveillance service deal with the company associated with themonitoring device, and connects it to the network, step 816. Themonitoring device, the control server and the service server thenperforms the steps of any of the embodiments described earlier in thisapplication and eventually creates a service connection to the serviceserver, step 818. When the service connection is up and running the usermay log in, step 820, to the service server from a user terminal byeither identifying a service account or the monitoring device. The usermay log in by entering user name and user authenticating code, byentering an identifier of the monitoring device combined with a userauthenticating code, etc. When the user has logged in he may access datafrom the monitoring device stored in the service server, access livedata from the monitoring device, or send instructions to the monitoringdevice.

In FIG. 13 another example of a scenario for connecting a monitoringdevice to a service server and providing access for a user to themonitoring device is described. In the scenario a monitoring device ismanufactured and in the manufacturing process a unique identity code anda unique key is stored in the monitoring device, step 910. The identitycode and the unique key have been described earlier in the application.The manufacturer also stores the identity code and the unique key in adata base of a control server, step 912. A user buys the camera andconnects it to the network, step 914. The user also logs in to a serviceprovider site by using an identity code and a user authentication codeprovided with the camera, step 916. When the identity code and the userauthentication code has been received by the service provider theservice provider sends instructions, including the identity code and theuser authentication code entered by the user, to a control server forassociating a monitoring device associated with the identity code andhaving a key valid for the authentication code to the service providersending the instruction, step 918. The step 914 of connecting themonitoring device to the network may be performed after the steps 916and 918. The monitoring device, the control server and the serviceserver then performs the steps of any of the embodiments describedearlier in this application and eventually creates an service connectionto the service server, step 818. When the service connection is up andrunning the user may log in, step 820, to the service server from a userterminal by either identifying a service account or the monitoringdevice. The log in may be performed by entering user name and userauthenticating code, by entering an identifier of the monitoring devicecombined with a user authenticating code, etc. When the user has loggedin he may access data from the monitoring device stored in the serviceserver, access live data from the monitoring device, or sendinstructions to the monitoring device.

In FIG. 14 an example of handovers of the monitoring device from aserver to another server is shown. In the context of this applicationhandover of the monitoring device means that a server, which iscommunicating with the monitoring device, provides an address to themonitoring device and that the monitoring device sends a connectionmessage to the server at the received address and, thus, the monitoringdevice starts to communicate with the new server given by the previousserver. In the figure each arrow indicates that the server from whichthe arrow originates sends the address of the server that the arrowpoints at to the monitoring device and the monitoring device then send aconnection message to this server.

Its evident from FIG. 12 that the system of the invention may be used toimplement lot of different structures, which may be easily changed ifnecessary. There is a limited number of servers presented in the figurefor facilitating the understanding, at least some of the servers mayprobably include references to many more servers than is depicted in thefigure.

In the example structure of FIG. 12 the system includes two initialcontrol servers, named control server 30:1 and control server 30:2respectively. These servers may both be initial manufacturer servers,i.e. servers having their address preprogrammed into the monitoringdevice during manufacture. A control server 30 may be a server arrangedto act as nothing else but a control server 30 according to the presentinvention, e.g. control server 30:1, but a control server may as wellperform other tasks simultaneously, i.e. such a control server maycertainly operate as another kind of server simultaneously and for otherpurposes. Further, a control server may be arranged as a control server30, as previously described, but having service servers 40 arranged atthe same site, in the same room, or in the same cabinet, e.g. controlservers 30:2, 30:3, and 30:6. Additionally, a control server 30 may bearranged as a combined control server 30 and a service server 40, e.g.control server 30:4, 30:7. Also an initial control server 30 may bearranged as a combined control server 30 and service server 40, notshown in the figure.

As stated above, both control server 30:1 and 30:2 may be initialcontrol servers 30 managed by the manufacturer of the monitoring devicesor any other party interested in providing the overall service andmanagement of such a monitoring system. In order to facilitate theunderstanding of FIG. 12 and the function and advantages of the system ahandover path from the control server will be followed. The monitoringdevice is automatically connected to control server 30:1 as it isinstalled and initiated, i.e. the address of control server 30:1 is thetop priority address of the list of addresses stored in the monitoringdevice in connection with manufacturing of the device. In this examplethe database associated to the control server 30:1 only includes twoentries, one entry including the address to the service provider controlserver 30:3 and one entry including the address to the service providercontrol server 30:4. Lets assume the identifier of the monitoring deviceis matched to the service provider control server 30:3. Then the controlserver 30:1 sends the address of control server 30:3 to the monitoringdevice and the monitoring device sends a connection message to thecontrol server 30:3. At control server 30:3 of the service provider theidentifier of the monitoring device is once more matched to entries in adatabase, this time a database of the service provider. The monitoringdevice is matched to the most suitable service server 40:1-40:3 or yetanother control server 30:6-30:7, those servers are the ones availableaccording to the handover arrows of the figure. In this example weassume the control server matches the monitoring device to the serviceserver 40:3 and send the address of this service server to themonitoring device. Then the monitoring device and the service serverestablishes a service connection as described above.

The monitoring system may easily and advantageously be provided withbackup servers, i.e. control servers providing redundancy in the system.Such backup servers may be implemented on all levels, i.e. both forinitial control servers and for lower level control servers. The backupserver may be a dedicated backup server or a control server normallyserving another region or other users.

The foregoing description of a preferred embodiment of the invention hasbeen presented for purposes of illustration and description. It is notintended to be exhaustive or to limit the invention to the precise formsdisclosed. Obviously many modifications and variations will be apparentto practitioners skilled in this art. It is intended that the scope ofthe invention be defined by the following claims and their equivalents.

1. A method for connecting a monitoring device to a service server, saidmethod comprising: retrieving an address relating to a control serverfrom a memory of the monitoring device, sending a connection messagefrom the monitoring device to the address relating to a control serverin response to a connecting event occurring at the monitoring device,extracting, at the control server, an identifier from the communicationbetween the monitoring device and the control server, identifying, atthe control server, a service server associated with the extractedidentifier, sending an address relating to the identified service serverfrom the control server to the monitoring device, sending a connectionmessage from the monitoring device to the identified service server inresponse to the receipt of the address related to the identified serviceserver, establishing a service connection between the monitoring deviceand the identified service server.
 2. The method of claim 1, whereinfurther an initial retrieval of an address relating to a control serverfrom a memory of the monitoring device returns a preconfigured addressrelating to a control server and wherein an initial sending of aconnection message from the monitoring device to the preconfiguredaddress is performed in response to an initiation event at themonitoring device.
 3. The method of claim 1, wherein further the sendingof a connection message from the monitoring device to a control serveris performed at least one time prior to sending a connection messagefrom the monitoring device to a control server which provides an addressof a service server to the monitoring device.
 4. The method of claim 1,wherein said extracting of an identifier further includes extracting anetwork address relating to the monitoring device from the communicationbetween the monitoring device and the control server, and wherein saididentifying of a service server further includes matching the extractednetwork address to a service server.
 5. The method of claim 1, whereinsaid extracting of an identifier further includes: extracting anidentification code included by the monitoring device in thecommunication between the monitoring device and the control server, andwherein said identifying of a service server further includes matchingthe extracted identification code to a service server.
 6. The method ofclaim 2, wherein the act of sending a connection message from themonitoring device to a preconfigured address relating to a controlserver is performed in response to the monitoring device detecting anetwork connection.
 7. The method of claim 2, wherein the act of sendinga connection message from the monitoring device to a preconfiguredaddress relating to an control server is performed in response to amanual actuation of a control means arranged at the monitoring device.8. The method of claim 2, wherein the act of sending the addressrelating to the identified service server includes sending the addressrelating to the identified service server in a reconfiguration messageto the monitoring device, and wherein the method further includessetting, in the monitoring device, an address used in response to theinitiation event to the address relating to the identified serviceserver.
 9. The method of claim 1, further comprising sending ofmonitoring information from the monitoring device to the service serverover the established service connection.
 10. The method of claim 9wherein the sending of monitoring information includes sending videodata from the monitoring device to the service server via theestablished service connection.
 11. A monitoring system comprising: amonitoring device, a control server, a plurality of service servers anda network connecting the servers and the monitoring device, wherein themonitoring device includes: a memory including a connection address,initiating means arranged to send a connection message over the networkto the connection address in response to an initiation event, and meansarranged to send a new connection message to an address received in amessage via said network, wherein the control server includes: anidentity extractor arranged to extract an identifier from acommunication between the monitoring device and the control server,matching means arranged to match the extracted identifier to a controlserver or a service server and retrieve an address to the matchedservice server, and a message generator arranged to generate a messageincluding the retrieved address and to send the generated message to themonitoring device, and wherein each service server includes: means forreceiving and processing monitoring data from a monitoring device. 12.The monitoring system of claim 11, wherein the monitoring systemincludes a plurality of control servers, the plurality of controlservers includes at least one initial control server, which is a highlevel control server in an hierarchy of control servers, arranged toaccess address information enabling at least indirect connection to anycontrol server and service server in the system.
 13. The monitoringsystem of claim 12, wherein the monitoring system includes at least twoinitial control servers.
 14. The monitoring system of claim 11, whereinthe identifier is an IP-address.
 15. The monitoring system of claim 11,wherein the identifier is an identification code stored in themonitoring device.
 16. The monitoring system of claim 11, wherein theinitiating means of the monitoring device is a network connectiondetector.
 17. The monitoring system of claim 11, wherein the initiatingmeans of the monitoring device is an actuator for manual actuation. 18.A control server for a monitoring system comprising: an interfaceconnecting the server to a network; an identity extractor arranged toextract an identifier from a message received from a monitoring device;matching means arranged to match the extracted identifier to a controlserver or a service server and retrieve an address to the matchedservice server; and a message generator arranged to generate a messageincluding the retrieved address.
 19. The control server for a monitoringsystem of claim 18, wherein the identifier is an IP-address.
 20. Thecontrol server for a monitoring system of claim 18, wherein theidentifier is an identification code received from the monitoringdevice.
 21. A monitoring device comprising: a memory including anaddress associated to a control server, an initiation means arranged tosend a connection message over the network to said address in responseto an initiation event, and means arranged to send a new connectionmessage to an address received in a message via said network in responseto the receipt of said received message.
 22. The monitoring device ofclaim 21, further including an identifier stored in the memory, themonitoring device being arranged to send this identifier to the addressto which the connection message is sent.
 23. The monitoring device ofclaim 22, wherein the identifier is an identity code.
 24. The monitoringdevice of claim 21, wherein the memory of the monitoring device includesa prioritized list of addresses indicating possible control servers.